[Fixed] vavoom and gcc3.2

Forum

[Fixed] vavoom and gcc3.2

Tue, 08 Oct 2002 02:39:59

Duke42

OK, here is my problem compiling vavoom under Gentoo-1.4 (with gcc3.2). "make" fails with: --- In file included from constexp.cpp:28: vcc.h:85: conflicting types for `enum error_t' /usr/include/errno.h:69: previous declaration as `typedef int error_t' make[1]: *** [constexp.o] Fehler 1 make[1]: Verlassen des Verzeichnisses Verzeichnis �/usr/src/vavoom/utils/vcc� make: *** [utils] Fehler 2 --- now, changing "error_t" to "error_vvt" gets my past this - after deleting everything because "make clean" doesn't work. Now, there are many unresolved symbols: --- gcc -s -o ../bin/vcc cmdlib.o constexp.o error.o expressn.o info.o name.o parse.o pcode.o token.o types.o vcc.o vcpp/libcpp.a cmdlib.o: In function `__static_initialization_and_destruction_0(int, int)': cmdlib.o(.text+0x110): undefined reference to `std::ios_base::Init::Init[in-charge]()' cmdlib.o: In function `__tcf_0': cmdlib.o(.text+0x539): undefined reference to `std::ios_base::Init::~Init [in-charge]()' cmdlib.o(.eh_frame+0x11): undefined reference to `__gxx_personality_v0' constexp.o: In function `__static_initialization_and_destruction_0(int, int)': constexp.o(.text+0x20): undefined reference to `std::ios_base::Init::Init[in-charge]()' constexp.o: In function `__tcf_0': constexp.o(.text+0x299): undefined reference to `std::ios_base::Init::~Init [in-charge]()' constexp.o(.eh_frame+0x11): undefined reference to `__gxx_personality_v0' error.o: In function `__static_initialization_and_destruction_0(int, int)': error.o(.text+0x20): undefined reference to `std::ios_base::Init::Init[in-charge]()' error.o: In function `__tcf_0': error.o(.text+0x4c9): undefined reference to `std::ios_base::Init::~Init [in-charge]()' error.o(.eh_frame+0x11): undefined reference to `__gxx_personality_v0' expressn.o: In function `__static_initialization_and_destruction_0(int, int)': expressn.o(.text+0x1f1c): undefined reference to `std::ios_base::Init::Init[in-charge]()' expressn.o: In function `ParseIFunctionCall(TTree*)': expressn.o(.text+0x213b): undefined reference to `operator new(unsigned)' expressn.o: In function `ParseExpressionPriority14()': expressn.o(.text+0x22e2): undefined reference to `operator new(unsigned)' expressn.o(.text+0x2365): undefined reference to `operator new(unsigned)' expressn.o(.text+0x2442): undefined reference to `operator new(unsigned)' expressn.o(.text+0x24e5): undefined reference to `operator new(unsigned)' expressn.o(.text+0x2574): undefined reference to `operator delete(void*)' expressn.o: In function `ParseExpressionPriority10()': expressn.o(.text+0x25de): undefined reference to `operator new(unsigned)' --- and so on --- this list is about 6x40 lines long. I don't want to paste the whole here - it's long enough already ... plus I'm getting this before in the make (but it's only a warning): --- /usr/include/g++-v32/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning use -Wno-deprecated. --- This comes about 20 times. So, what now? Duke42.

Tue, 08 Oct 2002 03:38:33

Janis Legzdinsh

The linker problem is fixed by adding -lstdc++ to the linker options. As of iostream headers - I got rid of them already. You can remove them from cmdlib.h, but that may require some other changes, or you can replace them to the new style includes.